Skip to content

docs: add Latitude observability integration - #6009

Open
guillemwilly wants to merge 1 commit into
crewAIInc:mainfrom
guillemwilly:add-latitude-observability
Open

docs: add Latitude observability integration#6009
guillemwilly wants to merge 1 commit into
crewAIInc:mainfrom
guillemwilly:add-latitude-observability

Conversation

@guillemwilly

@guillemwilly guillemwilly commented Jun 2, 2026

Copy link
Copy Markdown

Summary

Adds a Latitude observability integration guide, alongside the existing CrewAI observability integrations (Langfuse, Arize Phoenix, Langtrace, etc.).

  • New page: docs/en/observability/latitude.mdx — instruments CrewAI with the OpenInference CrewAIInstrumentor and exports OTLP spans to Latitude. Modeled on the existing Arize Phoenix / Langfuse pages (same "What is...?" intro, 5-step structure, References).
  • Overview: adds a Latitude card to docs/en/observability/overview.mdx under Monitoring & Tracing Platforms.
  • Navigation: adds en/observability/latitude after en/observability/langfuse in docs/docs.json (all English versions).

About Latitude

Latitude is an open-source (MIT-licensed) platform for improving production AI agents — observability, search, and evaluation. Its ingestion endpoint speaks standard OpenTelemetry (OTLP over HTTP), so CrewAI traces flow in via the OpenInference instrumentor without a vendor-specific library.

Test plan

  • Page renders under Observability in the docs nav
  • Latitude card appears on the Observability overview page
  • Code sample follows the same OpenInference pattern as the Arize Phoenix page

@coderabbitai

coderabbitai Bot commented Jun 2, 2026

Copy link
Copy Markdown

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8678643a-ca34-4d51-917e-bf646f14234a

📥 Commits

Reviewing files that changed from the base of the PR and between 1312352 and 8005330.

📒 Files selected for processing (1)
  • docs/docs.json
💤 Files with no reviewable changes (1)
  • docs/docs.json

📝 Walkthrough

Walkthrough

This change adds a single new slug entry, "edge/en/observability/latitude", to the observability list in docs/docs.json, placed immediately after the existing "edge/en/observability/truefoundry" entry.

Changes

Latitude Documentation Navigation

Layer / File(s) Summary
Documentation index wiring
docs/docs.json
Adds the "edge/en/observability/latitude" slug immediately after "edge/en/observability/truefoundry" in a repeated observability list.

Related Issues: None specified.

Related PRs: None specified.

Suggested Labels: documentation

Suggested Reviewers: None specified.


🐇 A tiny slug hops into place,
Right after truefoundry's space,
No code to break, no logic to bend,
Just one more path for docs to send.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: adding a Latitude observability integration in docs.
Description check ✅ Passed The description is directly about the Latitude observability docs update and matches the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/en/observability/latitude.mdx`:
- Around line 107-117: Update the hard-coded year in the Task sample: change
task1's description (the Task instance referenced as task1 and its description
string) to remove "in 2024" and use a year-agnostic phrase such as "latest" or
"recent advancements" (e.g., "Conduct a comprehensive analysis of the latest
advancements in AI" or "Conduct a comprehensive analysis of recent advancements
in AI"), ensuring the expected intent and wording remain the same and no other
references to the year are left in the Task definition.
- Around line 24-37: Add SERPER_API_KEY to the environment setup so the example
can run from a clean environment and remove the hardcoded phrase "AI in 2024" in
the Task description; specifically, update the env block to set SERPER_API_KEY
(used by SerperDevTool()) alongside LATITUDE_API_KEY, LATITUDE_PROJECT, and
OPENAI_API_KEY, and replace the stale wording "latest advancements in AI in
2024" with a timeless prompt (e.g., "latest advancements in AI") in the Task
text where SerperDevTool is instantiated.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f45a6842-a5a7-48d7-a200-9686638fbf61

📥 Commits

Reviewing files that changed from the base of the PR and between 774fd87 and 56adaf9.

📒 Files selected for processing (3)
  • docs/docs.json
  • docs/en/observability/latitude.mdx
  • docs/en/observability/overview.mdx

Comment thread docs/edge/en/observability/latitude.mdx
Comment thread docs/edge/en/observability/latitude.mdx
@guillemwilly

Copy link
Copy Markdown
Author

Thanks for the review! Addressed both in f2558c6:

  • Added SERPER_API_KEY to the Step 2 env block so the example runs from a clean environment (it's used by SerperDevTool() in Step 4).
  • Replaced the hard-coded "AI in 2024" with a year-agnostic prompt.

Adds a Latitude integration guide under observability and registers it in
the edge navigation and the observability overview. Latitude ingests CrewAI
traces over standard OTLP via OpenInference.

Retargeted onto the new versioned docs layout (edge/en) after the docs
restructure.
@guillemwilly
guillemwilly force-pushed the add-latitude-observability branch from 1312352 to 8005330 Compare July 2, 2026 08:33
@guillemwilly

Copy link
Copy Markdown
Author

Rebased onto the new versioned docs layout. The earlier approved version targeted the old flat docs/en/observability path, which no longer exists after the docs restructure, so this now adds the integration under docs/edge/en/observability and registers it in the edge navigation and overview. Ready for another look whenever convenient.

@github-actions

Copy link
Copy Markdown
Contributor

This PR is stale because it has been open for 45 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant